UMBRA 3.0.1 - SEPARATE TEST BUILD

Start: E:\Umbra 3\Starta Umbra 3.cmd
Your previous E:\Umbra installation is retained.
Do not run both bot versions against the same game client. When switching bot
versions, close the old bot and restart Retronic before attaching the new one.
The existing license is still required. Startup remains paused.

3.0.1 fixes the activation field truncating a complete 67-character license key.
Paste the entire key including UM-. Your administrator-issued key remains valid;
you do not need to enter an email address or create a separate account.

CAVEBOT STUDIO
Open Cavebot Studio in the dashboard header.
Hunting variants are shown separately from the bank/depot route.

1. Stand at a safe start point for the hunting loop. Keep Walker off.
2. Record a hunting route, walk the complete loop and return to the start tile.
   Finish the recording and give the route a recognizable name.
3. Repeat from the same tile for the other variants. Follow the same main loop
   and use the same stairs, rope spots and other fixed actions. Variants may
   have different numbers of nodes, but must stay within eight tiles of the
   reference route in the same order. The first route is the reference.
4. Save the plan as a .u3routes file. Apply it to Walker. Resume Umbra only when
   ready, then start Cavebot. It selects a complete recorded variant at each
   loop boundary, without choosing the same variant twice in succession when
   there are alternatives. It never invents random map coordinates.

DEPOSITER
Record or import the shared trip from the hunting start point to the bank/depot
and back. Put NPC dialogue, waits, Lua actions and deposit actions in this section.
The route editor retains the original Walker action syntax and raw labels.
Enable the capacity condition and set the threshold, for example cap below20.
The check happens at the end of the hunting loop, before starting another one.
The bank/depot section is never randomized. Keep its actions and labels in order.
Only enable the condition once the whole trip back to the hunting anchor is ready.

EXISTING PROFILES
File > Open still loads your normal TXT bot settings. Cavebot Studio can import
the waypoints from a TXT profile; review the split between hunting and deposit.
The new multi-route plan is saved separately as .u3routes. Save both your normal
TXT settings and your route plan. Loading a plan does not start the bot.
Manual edits to an applied Walker list stop automatic variant replacement so
that your edited list is not silently overwritten. Re-apply the plan when ready.

LOOT TIMING
The default waits400-900ms before opening most bodies, sometimes up to1500ms.
This is one extra wait per body, not per item/coin stack. Network response and
the existing item moves add their normal time. Healing and pause are not blocked
by this wait. Configure the range or disable it in Cavebot Studio.

RUNE MAKER / SPELL TRAINER
Use the Rune / Spell Trainer button in the dashboard header.
Rune Maker equips blank runes through the existing engine. Spell Trainer only
casts the entered spell; it does not require or move blank runes.

Mana mode: enter a minimum percentage and an upward variation. For example40
with variation6 samples one threshold from40% through46%. That threshold stays
fixed while mana rises; another is selected after the cast is observed.
Time mode: wait the entered number of seconds between casts. Minimum mana is
still required. Both modules share a casting guard so they cannot cast at once.
Failed attempts back off instead of sending a spell on every engine tick.
Global Pause and license checks always take priority. Applying settings never
resumes a paused bot. Verify the spell and mana values for your character.

FIRST LIVE TEST
Use a safe, short route first. Confirm one recorded loop and Stop, then test a
second variant. Test the deposit route separately with items you can afford to
move. Confirm one Rune Maker or Spell Trainer cast before enabling both.
The build has offline checks; pathfinding, NPC dialogue, inventory actions and
spell outcomes must still be confirmed with your actual character/server.

Varying timing or paths does not guarantee that automation is undetectable.
